Empirical Validation of a Software Requirements Specification Checklist
نویسندگان
چکیده
[Context/Motivation] For areas such as Government IT Procurement, the Software Requirements Specification (SRS) often forms the basis for a public procurement. In these cases, having domain knowledge is often mutually exclusive to knowing RE. Domain experts lacking the necessary RE experience face issues assessing the quality and correctness of the SRS. This especially forms a problem for situations where the SRS acts as the base for a proposal and resulting contract, which is why often third party RE experts are consulted for evaluating the SRS beforehand. These experts are highly motivated to improve their process and offer a more uniform and better service. [Question/problem] Is our developed checklist a valid instrument to support the RE practitioner in the SRS validation process? [Principal ideas/results] We propose to empirically evaluate the checklist in a live study. Participants of our Evaluation Study are asked to simulate the validation of a sample SRS, guided by our checklist. We will analyze the data from a post-use questionnaire at the end of the session using a mixed method approach to assess the quality and usability of our checklist and its expected impact on the validation process. This assessment will be part of the overall validation of our checklist. [Expected Contribution] We expect to gain knowledge regarding the quality of our instrument. Secondly, this live study contributes to the validation, and thus the realization of a practical tool to be used by RE practitioners worldwide.
منابع مشابه
Técnicas de Inspeção de Documentos de Requisitos de Software: um Estudo Comparativo
This paper presents an empirical study on inspection of Software Requirements Specification (SRS) Documents, aiming at evaluate the efficiency of reading techniques applied to these documents. The techniques of Checklist, Scenario, and Perspective were comparatively evaluated, through the inspection of the SRS of a software application, performed by software engineers. The definition and execut...
متن کاملSoftware Engineering and Project Man Agement
Question: Difference between Verification and Validation? Answer: Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings. You CAN learn to do verification, with lit...
متن کاملTowards a unified checklist for empirical research in software engineering: first proposal
Background: Current checklists for empirical software engineering cover either experimental research or case study research but ignore the many commonalities that exist across all kinds of empirical research. Identifying these commonalities, and explaining why they exist, would enhance our understanding of empirical research in general and of the differences between experimental and case study ...
متن کاملUnderstanding Requirements for Open Source Software
This study presents findings from an empirical study directed at understanding the roles, forms, and consequences arising in requirements within open source software development efforts. Four open source software development communities are described, examined, and compared to help discover what these differences may be. At least two dozen kinds of software informalisms are found to play a crit...
متن کاملUnderstanding Requirements for Developing Open Source Software Systems
This study presents an initial set of findings from an empirical study of social processes, technical system configurations, organizational contexts, and interrelationships that give rise to open software. The focus is directed at understanding the requirements for open software development efforts, and how the development of these requirements differs from those traditional to software enginee...
متن کامل